Llm feature flag & memberlist caching - #59
Merged
Merged
Conversation
Because the "@bottomly" would be tokenised by slack, we need to lookup using the member repo. However, this would introduce a LOT of lookups and I always had vague thoughts of caching the member repo anyway. This commit adds memory caching to the member repo which is warmed at app startup. This way all the token replacements should be signficantly faster as all calls for member data should be obviated.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ensures the LLM integration flag is now controllable at runtime.
Adds a cache around the MemberRepository to reduce DB roundtrips